Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updating freyja to 1.5.2 #1082

Merged
merged 2 commits into from
Oct 29, 2024
Merged

updating freyja to 1.5.2 #1082

merged 2 commits into from
Oct 29, 2024

Conversation

erinyoung
Copy link
Contributor

There's a new version of Freyja!

1.5.2 was released last week, but it's stuck on bioconda - which is what 1.5.1 and prior dockerfiles use for installation with micromamba.

I copied the files from 1.5.1 and made several modifications. The original goal was to install freyja from source. Freyja has some common dependencies of samtools, ivar, and epiweeks which are fairly simple to install. I, however, have not been able to install usher from source (see #1014) , so I kept the base image as micromamba and then copied over the dependencies listed in the bioconda recipe and had all of those installed via micromamba.

Freyja is then downloaded with wget and installed via pip. Freyja's setup.py doesn't list all the python dependencies, so all the python dependencies (that I can find) are installed via micromamba.

Git is installed via apt-get because it is required when pip installs freyja.

I have also changed the github actions to update the workflow weekly instead of monthly, because I've been getting feedback that monthly just isn't often enough.

Pull Request (PR) checklist:

  • Include a description of what is in this pull request in this message.
  • The dockerfile successfully builds to a test target for the user creating the PR. (i.e. docker build --tag samtools:1.15test --target test docker-builds/samtools/1.15 )
  • Directory structure as name of the tool in lower case with special characters removed with a subdirectory of the version number (i.e. spades/3.12.0/Dockerfile)
    • (optional) All test files are located in same directory as the Dockerfile (i.e. shigatyper/2.0.1/test.sh)
  • Create a simple container-specific README.md in the same directory as the Dockerfile (i.e. spades/3.12.0/README.md)
    • If this README is longer than 30 lines, there is an explanation as to why more detail was needed
  • Dockerfile includes the recommended LABELS
  • Main README.md has been updated to include the tool and/or version of the dockerfile(s) in this PR
  • Program_Licenses.md contains the tool(s) used in this PR and has been updated for any missing

@Kincekara
Copy link
Collaborator

@erinyoung When I check conda requirements, some of the libraries seem missing: pytest, flake8, coveralls, and scipy. I am not sure if those are for the tests or the program itself. Could you check them again?

Please have mercy on my eyes and try not to use verbose (-vv) in pip installations. I can't follow the pip logs 👁️ 👁️

@erinyoung
Copy link
Contributor Author

pytest, flake8, coveralls, and scipy aren't in the bioconda recipe for 1.5.1 at https://bioconda.github.io/recipes/freyja/README.html and they aren't listed in their most-recent freyja PR into bioconda at https://github.com/bioconda/bioconda-recipes/pull/51511/files

@erinyoung
Copy link
Contributor Author

@Kincekara , I removed the -vv! Sorry!

@Kincekara
Copy link
Collaborator

Thank you for checking again. I believe those extra libraries are for the pytest. I have no further suggestions. The tests look good. I am merging and deploying this...

@Kincekara Kincekara merged commit 52c1c12 into master Oct 29, 2024
2 checks passed
@erinyoung erinyoung deleted the erin-freyja branch October 29, 2024 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants